Skip to content

MSC3124: Handling spoilers in plain-text message fallback#3124

Closed
xenofem wants to merge 2 commits intomatrix-org:old_masterfrom
xenofem:spoiler-fallback
Closed

MSC3124: Handling spoilers in plain-text message fallback#3124
xenofem wants to merge 2 commits intomatrix-org:old_masterfrom
xenofem:spoiler-fallback

Conversation

@xenofem
Copy link
Copy Markdown

@xenofem xenofem commented Apr 15, 2021

Signed-off-by: xenofem <xenofem@xeno.science>
@xenofem
Copy link
Copy Markdown
Author

xenofem commented Apr 15, 2021

This addresses matrix-org/matrix-spec#808.

@turt2live turt2live added client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec proposal A matrix spec change proposal proposal-in-review labels Apr 15, 2021
Signed-off-by: xenofem <xenofem@xeno.science>
@xenofem xenofem changed the title MSC3124: Representing spoilers in plain-text message fallback MSC3124: Handling spoilers in plain-text message fallback Apr 15, 2021
@xenofem
Copy link
Copy Markdown
Author

xenofem commented Apr 15, 2021

Following a discussion in #matrix-spec:matrix.org, I've revised this MSC to put responsibility on receiving clients to handle spoilers safely; it's been rightly pointed out that the MSC as originally drafted is unenforceable, so it isn't safe for clients to assume that other clients are compliant. The MSC still addresses matrix-org/matrix-spec#808 , but no longer makes any specific suggestions on how to obfuscate spoilers in fallback, since this obfuscation is not useful to receiving clients without a way to guarantee obfuscation is always being performed by all sending clients.

@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@xenofem xenofem closed this by deleting the head repository Mar 28, 2026
@turt2live turt2live added the abandoned A proposal where the author/shepherd is not responsive label Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

abandoned A proposal where the author/shepherd is not responsive client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants